-
Notifications
You must be signed in to change notification settings - Fork 183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch git submodules to Wally packages #584
Switch git submodules to Wally packages #584
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good.
One minor suggestion, remove the step for submodules on the workflows since the plugin part was the only one needing it:
uses: action/checkout@v3
- with:
- submodules: true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks good for release to me.
…ber/rojo into wally-package-management
@@ -2,7 +2,8 @@ | |||
Defines the errors that can be returned by the reconciler. | |||
]] | |||
|
|||
local Fmt = require(script.Parent.Parent.Parent.Fmt) | |||
local Packages = script.Parent.Parent.Parent.Packages |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This kinda line is why we use FindFirstAncestor("Rojo")
a lot. 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, this is a great migration!
Alright, so I hate to be the one to do this, but #584 broke crates.io publishing and also caused librojo to be unusable. I see that there was some discussion on Discord shortly after the problem was realized, but there was no action taken. I think keeping librojo and publishing working far, far outweigh any convenience added by Wally. I've kept the same `Packages` naming convention to keep the diff minimal.
* Switch git submodules to Wally packages * Update build snapshot * Add wally to foreman and use latest versions * Install packages in CI runners * Fix indents * Install packages in the correct directory * Install packages in correct dir of release action too * Remove submodules from ci checkout * Remove submodules from release checkout * Update selene with latest fix * Fix whitespace Co-authored-by: Lucien Greathouse <[email protected]>
Alright, so I hate to be the one to do this, but rojo-rbx#584 broke crates.io publishing and also caused librojo to be unusable. I see that there was some discussion on Discord shortly after the problem was realized, but there was no action taken. I think keeping librojo and publishing working far, far outweigh any convenience added by Wally. I've kept the same `Packages` naming convention to keep the diff minimal.
Removes the git submodules and moves to a more elegant solution with Wally.
Also migrates to @evaera's Promise. No compatibility issues arose, and plugin tests all pass.